home *** CD-ROM | disk | FTP | other *** search
- Compiler
-
- This is the most complex part of the operation, and typically the least reliable.
- given a .i file output by the preprocessor, or in the trivial case a .c file
- having no #includes or #defines, this stage will generate a .s file which consists
- of 68000 assembly language.
-
- To use the compiler, simply select a .i or valid .c text editor window and select
- the GCC/compile menu option. A new .s window will appear, together with a
- list of errors/warnings. This option may crash without warning in the event
- of low memory or various complicated conditions. Make sure you save your
- editor windows before invoking the compiler.
-
- Typically, you can ignore some warnings and still proceed to the next stage
- (assembly), but any errors reported will result in incorrect code generation,
- which will result in mysterious crashes or strange diagnostics when you
- try to assemble and/or link. Some warnings will prevent your program
- from working, so you are advised to investigate all diagnostics.
-
- Users familiar with the style of assembly language used in Apple documentation
- can invoke the GCC/compile (MPW) option to see their code generated.
- This output must not be used as input to the built-in assembler, but may be
- useful for debugging.